feat: Add ChannelKeeperV2 to IBC Keeper initialization #2562
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @vladjdk! Please check this PR whenever you have a free moment. |
|
Hi @leopardracer, tests are failing. Seems like the v2 stack isn't being initialized properly. Please refer to Gaia for a reference on how to add the stack: https://github.com/cosmos/gaia/blob/a1998b835eee371781a53fcdc911d05ee76e257c/app/keepers/keepers.go#L553 |
|
@vladjdk Hi! Just wanted to remind you about this PR. If you have some time, please take a look. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the IBC Keeper initialization to include ChannelKeeperV2 in the sovereign app. The change adds support for the new IBC channel keeper version while maintaining compatibility with the existing channel keeper implementation.
Changes:
This enhancement allows for improved IBC channel management capabilities while ensuring smooth integration with the existing IBC infrastructure.